se.cs.ieu.edu.tr
Course Name | |
Code | Semester | Theory (hour/week) | Application/Lab (hour/week) | Local Credits | ECTS |
---|---|---|---|---|---|
Spring |
Prerequisites | None | |||||
Course Language | ||||||
Course Type | Required | |||||
Course Level | - | |||||
Mode of Delivery | - | |||||
Teaching Methods and Techniques of the Course | ||||||
Course Coordinator | ||||||
Course Lecturer(s) | ||||||
Assistant(s) | - |
Course Objectives | |
Learning Outcomes | The students who succeeded in this course;
|
Course Description |
| Core Courses | X |
Major Area Courses | ||
Supportive Courses | ||
Media and Managment Skills Courses | ||
Transferable Skill Courses |
Week | Subjects | Required Materials |
1 | Engineering Economic Decisions | Fundamentals of Engineering Economics, Chapter 1 |
2 | Time Value of Money | Fundamentals of Engineering Economics, Chapter 2 |
3 | Time Value of Money | Fundamentals of Engineering Economics, Chapter 2 |
4 | Time Value of Money | Fundamentals of Engineering Economics, Chapter 2 |
5 | Understanding Money Management | Fundamentals of Engineering Economics, Chapter 3 |
6 | Equivalance Calculations Under Inflation | Fundamentals of Engineering Economics, Chapter 4 |
7 | Midterm Exam | |
8 | Present Worth Analysis | Fundamentals of Engineering Economics, Chapter 5 |
9 | Annual Equivalence Analysis | Fundamentals of Engineering Economics, Chapter 6 |
10 | Rate of Return Analysis | Fundamentals of Engineering Economics, Chapter 7 |
11 | Benefit-Cost Analysis | Fundamentals of Engineering Economics, Chapter 8 |
12 | Accounting for Depreciation and Income Taxes | Fundamentals of Engineering Economics, Chapter 9 |
13 | Project Cash Flow Analysis | Fundamentals of Engineering Economics, Chapter 10 |
14 | Review | |
15 | Review | |
16 | Review of the Semester |
Course Notes/Textbooks | Fundamentals of Engineering Economics, 3rd ed., Chan S. Park, PrenticeHall.. |
Suggested Readings/Materials | Contemporary Engineering Economics, Chan S. Park, 3rd ed., PrenticeHall.Engineering Economy, Leland Blank, Anthony Tarquin, McGrawHill.Principles of Engineering Economic Analysis, John A. White, Marvin H. Agee, Kenneth E. Case, Wiley. Lecture PowerPoint slides, Excel sheets supplied in lectures for example problems. |
Semester Activities | Number | Weigthing |
Participation | ||
Laboratory / Application | ||
Field Work | ||
Quizzes / Studio Critiques | 2 | 25 |
Portfolio | ||
Homework / Assignments | ||
Presentation / Jury | ||
Project | ||
Seminar / Workshop | ||
Oral Exam | ||
Midterm | 1 | 35 |
Final Exam | 1 | 40 |
Total |
Weighting of Semester Activities on the Final Grade | 60 | |
Weighting of End-of-Semester Activities on the Final Grade | 40 | |
Total |
Semester Activities | Number | Duration (Hours) | Workload |
---|---|---|---|
Course Hours (Including exam week: 16 x total hours) | 16 | 3 | 48 |
Laboratory / Application Hours (Including exam week: 16 x total hours) | 16 | ||
Study Hours Out of Class | 15 | 3 | |
Field Work | |||
Quizzes / Studio Critiques | 2 | 10 | |
Portfolio | |||
Homework / Assignments | |||
Presentation / Jury | |||
Project | |||
Seminar / Workshop | |||
Oral Exam | |||
Midterms | 1 | 18 | |
Final Exams | 1 | 24 | |
Total | 155 |
# | Program Competencies/Outcomes | * Contribution Level | ||||
1 | 2 | 3 | 4 | 5 | ||
1 | Be able to define problems in real life by identifying functional and nonfunctional requirements that the software is to execute | |||||
2 | Be able to design and analyze software at component, subsystem, and software architecture level | |||||
3 | Be able to develop software by coding, verifying, doing unit testing and debugging | |||||
4 | Be able to verify software by testing its behaviour, execution conditions, and expected results | |||||
5 | Be able to maintain software due to working environment changes, new user demands and the emergence of software errors that occur during operation | |||||
6 | Be able to monitor and control changes in the software, the integration of software with other software systems, and plan to release software versions systematically | |||||
7 | To have knowledge in the area of software requirements understanding, process planning, output specification, resource planning, risk management and quality planning | |||||
8 | Be able to identify, evaluate, measure and manage changes in software development by applying software engineering processes | |||||
9 | Be able to use various tools and methods to do the software requirements, design, development, testing and maintenance | |||||
10 | To have knowledge of basic quality metrics, software life cycle processes, software quality, quality model characteristics, and be able to use them to develop, verify and test software | X | ||||
11 | To have knowledge in other disciplines that have common boundaries with software engineering such as computer engineering, management, mathematics, project management, quality management, software ergonomics and systems engineering | X | ||||
12 | Be able to grasp software engineering culture and concept of ethics, and have the basic information of applying them in the software engineering | X | ||||
13 | Be able to use a foreign language to follow related field publications and communicate with colleagues | X |
*1 Lowest, 2 Low, 3 Average, 4 High, 5 Highest